[Snyk] Upgrade socket.io-client from 4.5.1 to 4.8.0 #100
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Snyk has created this PR to upgrade socket.io-client from 4.5.1 to 4.8.0. See this package in npm: socket.io-client See this project in Snyk: https://app.snyk.io/org/p4r4d0xshado/project/f28c3a8b-ef9d-404b-9fb0-90812d837979?utm_source=github&utm_medium=referral&page=upgrade-pr
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to upgrade socket.io-client from 4.5.1 to 4.8.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 15 versions ahead of your current version.
The recommended version was released on 23 days ago.
Release notes
Package name: socket.io-client
-
4.8.0 - 2024-09-21
import { io } from "socket.io-client";
Transport
Description
HTTP long-polling based on the built-in
HTTP long-polling based on the
HTTP long-polling based on the built-in
WebSocket transport based on the
WebSocket transport based on the built-in
WebTransport transport based on the built-in
Transport
browser
Node.js
Deno
Bun
✅
✅ (1)
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅ (2)
✅
✅
✅
✅
import { io } from "socket.io-client";
- when HTTP long-polling is disabled on the server, or if CORS fails
- when WebSocket is tested first (with
- accept string | undefined as init argument (bis) (60c757f)
- allow to manually stop the reconnection loop (13c6d2e)
- close the engine upon decoding exception (04c8dd9)
- do not send a packet on an expired connection (#5134) (8adcfbf)
-
4.7.5 - 2024-03-14
-
4.7.4 - 2024-01-12
-
4.7.3 - 2024-01-03
-
4.7.2 - 2023-08-02
-
4.7.1 - 2023-06-28
-
4.7.0 - 2023-06-22
-
4.6.2 - 2023-05-31
-
4.6.1 - 2023-02-20
-
4.6.0 - 2023-02-06
-
4.6.0-alpha2 - 2023-02-04
-
4.6.0-alpha1 - 2023-02-03
-
4.5.4 - 2022-11-22
-
4.5.3 - 2022-10-15
-
4.5.2 - 2022-09-02
-
4.5.1 - 2022-05-17
from socket.io-client GitHub release notesFeatures
Custom transport implementations
The
transportsoption now accepts an array of transport implementations:import { XHR, WebSocket } from "engine.io-client";
const socket = io({
transports: [XHR, WebSocket]
});
Here is the list of provided implementations:
Fetchfetch()method.NodeXHRXMLHttpRequestobject provided by thexmlhttprequest-sslpackage.XHRXMLHttpRequestobject.NodeWebSocketWebSocketobject provided by thewspackage.WebSocketWebSocketobject.WebTransportWebTransportobject.Usage:
FetchNodeXHRXHRNodeWebSocketWebSocketWebTransport(1) since v18.0.0
(2) since v21.0.0
Added in f4d898e and b11763b.
Test each low-level transports
When setting the
tryAllTransportsoption totrue, if the first transport (usually, HTTP long-polling) fails, then the other transports will be tested too:const socket = io({
tryAllTransports: true
});
This feature is useful in two cases:
transports: ["websocket", "polling"])The only potential downside is that the connection attempt could take more time in case of failure, as there have been reports of WebSocket connection errors taking several seconds before being detected (that's one reason for using HTTP long-polling first). That's why the option defaults to
falsefor now.Added in 579b243.
Bug Fixes
Dependencies
engine.io-client@~6.6.1(diff and diff)ws@~8.17.1(diff)Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: